Skip to content

Comments

Update dependency markdownlint-cli2 to v0.20.0#332

Merged
renovate[bot] merged 1 commit into1.44.xfrom
renovate/all-minor-patch
Dec 8, 2025
Merged

Update dependency markdownlint-cli2 to v0.20.0#332
renovate[bot] merged 1 commit into1.44.xfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 8, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
markdownlint-cli2 0.19.1 -> 0.20.0 age adoption passing confidence

Release Notes

DavidAnson/markdownlint-cli2 (markdownlint-cli2)

v0.20.0

Compare Source

  • Update dependencies

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

Read more information about the use of Renovate Bot within Laminas.

| datasource | package           | from   | to     |
| ---------- | ----------------- | ------ | ------ |
| npm        | markdownlint-cli2 | 0.19.1 | 0.20.0 |


Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot added the renovate label Dec 8, 2025
@gsteel gsteel self-assigned this Dec 8, 2025
@gsteel gsteel added this to the 1.44.0 milestone Dec 8, 2025
@gsteel gsteel added dependencies Pull requests that update a dependency file and removed renovate labels Dec 8, 2025
@gsteel
Copy link
Member

gsteel commented Dec 8, 2025

@froschdesign

Merging this will cause errors anywhere markdown tables are used that don't have columns that all line up nicely: MD060/table-column-style

Question: Should we merge this as-is and accept the CI failures on the basis that users can use their own .markdownlint.json file, or should we amend the shipped .markdownlint.json file to configure this issue so we don't get any CI failures in our repos?

IMO, merging this as-is is likely best as it will enforce tables that look pretty in source files, and, PHPStorm for example can take care of this with a 'quick fix'

@renovate renovate bot merged commit 852c6f0 into 1.44.x Dec 8, 2025
4 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch December 8, 2025 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant